Using log data to train for automated sourcing

ABSTRACT

Techniques for using recruiter review data to create training, validation and test sets for automated sourcing are described. An example system obtains sample suggested candidate member profiles and sample search result member profiles in an online system. The system identifies unique pairs of member profiles, each pair consisting of one of the suggested candidate profiles and one of the search result profiles. Additionally, the system generates a label for each of the unique pairs of profiles. The label is generated using a score generated from log information of the online system, the log information including historical records of searcher feedback regarding members of the online system, the score being higher if the searcher accepted the sample search result member profile in a search session. Furthermore, the system inputs the labels into a machine learning algorithm to train a combined ranking model that outputs ranking scores for search result member profiles.

PRIORITY CLAIM

This application claims the benefit of priority to U.S. Provisional Patent Application No. 62/460,622 entitled “Using Log Data to Train for Automated Sourcing”, [reference number 901992-US-PSP (3080.H86PRV)] filed Feb. 17, 2017, which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

The present disclosure generally relates to computer technology for solving technical challenges in search queries to data sources. More specifically, the present disclosure relates to using historical log data to generate training data for candidate search ranking algorithms and models.

BACKGROUND

The rise of the Internet has occasioned two disparate phenomena: the increase in the presence of social networks, with their corresponding member profiles visible to large numbers of people, and the increase in use of social networks for job searches, both by applicants and by employers. Employers, or at least recruiters attempting to connect applicants and employers, often perform searches on social networks to identify candidates who have qualifications that make them good candidates for whatever job opening they are attempting to fill. The employers or recruiters then can contact these candidates to see if they are interested in applying for the job opening.

Traditional querying of social networks for candidates involves the employer or recruiter entering one or more search terms to manually create the query. A key challenge in talent search is to translate the criteria of a hiring position into a search query that leads to desired candidates. To fulfill this goal, the searcher has to understand which skills are typically required for the position, what the alternatives are, which companies are likely to have such candidates, which schools the candidates are most likely to graduate from, etc. Moreover, this knowledge varies over time. As a result, it is not surprising that even for experienced recruiters, it often requires many searching trials in order to obtain a satisfactory query.

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments of the technology are illustrated, by way of example and not limitation, in the figures of the accompanying drawings.

FIG. 1 is a block diagram illustrating a client-server system, in accordance with an example embodiment.

FIG. 2 is a block diagram showing the functional components of an online system hosting a social networking service, including a data processing block referred to herein as a search engine, for use in generating and providing search results for a search query, consistent with some embodiments of the present disclosure.

FIG. 3 is a block diagram illustrating an application server block of FIG. 2 in more detail, in accordance with an example embodiment.

FIG. 4 is a block diagram illustrating a skills generator in more detail, in accordance with an example embodiment.

FIG. 5 is a diagram illustrating an offline process to estimate expertise scores, in accordance with another example embodiment.

FIG. 6 is a block diagram illustrating a search results ranker in more detail, in accordance with an example embodiment.

FIG. 7 is a block diagram illustrating a search results ranker in more detail, in accordance with another example embodiment.

FIG. 8 is a flow diagram illustrating a method for performing a suggested candidate-based search in accordance with an example embodiment.

FIG. 9 is a flow diagram illustrating generating a search query based on extracted one or more attributes, in accordance with an example embodiment.

FIG. 10 is a flow diagram illustrating a method of ranking search results using suggested candidates in accordance with an example embodiment.

FIG. 11 is a flow diagram illustrating a method for generating labels for sample suggested candidate member profiles in accordance with an example embodiment.

FIG. 12 is a flow diagram illustrating a method of dynamically training weights of a machine learning algorithm model in accordance with an example embodiment.

FIG. 13 is a screen capture illustrating a first screen of a user interface for performing a suggested candidate-based search in accordance with an example embodiment.

FIG. 14 is a screen capture illustrating a second screen of the user interface for performing a suggested candidate-based search in accordance with an example embodiment.

FIG. 15 is a block diagram illustrating a representative software architecture, which may be used in conjunction with various hardware architectures herein described.

FIG. 16 is a block diagram illustrating components of a machine, according to some example embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

DETAILED DESCRIPTION

The present disclosure describes, among other things, methods, systems, and computer program products that individually provide various functionality. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the various aspects of different embodiments of the present disclosure. It will be evident, however, to one skilled in the art, that the present disclosure may be practiced without all of the specific details.

One of the most important challenges for recruiting tools is to identify the relevant product logs from eco-systems and platforms used with the tools that could help train and test machine-learned models for automated sourcing and intelligent matching. As many existing recruiting products do not have a streaming interface or produce candidate streams, it can be difficult to approximate a user's (e.g., a recruiter's) search session. Embodiments disclosed herein use recruiter review data to create training, validation and test sets for automated sourcing.

As used herein, in certain embodiments, the terms ‘automated sourcing’, ‘intelligent matches’ and ‘intelligent matching’ refer to systems and methods that offer intelligent candidate suggestions to users such as, for example, recruiters, hiring managers, and small business owners. Automated sourcing enables such users to review and select relevant candidates from a candidate stream without having to navigate through or review a large list of candidates. For example, automated sourcing can provide a user with intelligent suggestions automatically selected from a candidate stream or flow of candidates for a position to be filled without requiring the user to manually move through a list of thousands of candidates. In the automated sourcing and intelligent matches contexts, such a candidate stream can be created based on minimal initial contributions or inputs from users such as small business owners and hiring managers.

Techniques are disclosed that utilize user log data from a recruiter tool to create training, validation, and test datasets for machine-learned models for automated sourcing. The recruiter tool log data can include historical data such as recruiter review logs from the automated sourcing tool, an intelligent matches application, or an intelligent matching product. In an embodiment, the recruiter review data is re-purposed while taking into account changes in standardization and ranking signals on the profiles over time. According to an embodiment, a ‘time machine’ user defined function (UDF) takes a member's profile and timeline from standardized data and generates a timeline for position-derived data and education-derived data. The UDF includes an AsOf(timestamp) function that uses member profile data to provide a snapshot of the member profile as of a certain day in the past. The UDF also includes Between(start, end) function that produces a member timeline as specified by the two epochs (i.e., start and end).

In an embodiment, a recruiting tool product provides a capability to associate a manager user or seat with each recruiter user or seat that uses the tool. Based on this association, a recruiter could then selectively bookmark a number of prospects/candidates and send them for review by the manager. A manager could then provide specific feedback and could instruct the recruiter either to proceed with contacting the candidate or to end the conversation. This review data can be saved in recruiting tool log files or data stores. This review data (i.e., project review data or log data) can be used as a proxy to a stream use case that is supported in automated sourcing and intelligent matching. Embodiments enable use of project review data that is dated. For example, embodiments can use historical log data going back several years (e.g., 2-10 years) to train for automated sourcing. Embodiments also overcome issues related to using project review data that may not have complete coverage (i.e. data structures with incomplete data fields). Embodiments assume rational behavior and evidence-based refinements of candidate queries by a user (e.g., a recruiter). Embodiments also assume that each recruiting or staffing project is used to hire for a single position (e.g., projects seek to fill a single job opening).

Embodiments can use log data from past years (e.g., from the past 2 years or more). In a non-limiting embodiment, log data from the past 8 years may be used to train ranking algorithms used by an automated sourcing tool or an intelligent matches tool. By using such historical log data to train ranking algorithms used by an automated sourcing tool, embodiments provide an evolution over time of feedback from an end-user (e.g., a recruiter) in addition to implicit feedback from an ultimate decision maker (e.g., a hiring manager).

Some embodiments use time snapshot of time series data over time. For example, in a case where a candidate was suggested 6 years ago and was presented by a recruiter user to a hiring manager, use of time series data derived from log data enables a current user to look at a timeline. These embodiments overcome issues with historical data that may be stale. The staleness issue can be overcome by going back in time in a timeline and projecting that past data into a current candidate stream. Timelines may not be provided for candidate features such as, for example, skills, but embodiments can take recruiter logs to determine positive and negative reactions (e.g., feedback) for a position similar to the position an organization is currently seeking to fill. An embodiment can map titles over time to skills to overcome an issue with logs not indicating timelines of candidate skills.

As some recruiting application log data is free form text, an embodiment characterizes log data. In one example, sentiment analysis of free form text can be performed to characterize sentiments (e.g., candidate rejection, deferral, or acceptance feedback) provided by hiring manager and/or recruiters.

An embodiment uses search logs in a streaming context. That is, logs can be repurposed for an automated sourcing system that provides candidate streams. For example, an embodiment can build up a taxonomy of words from log data to train ranking algorithms for automated sourcing. Embodiments approximate a candidate profile at different points in time by invoking a time machine function or block that uses past log data.

As an example, log data regarding past feedback for a candidate is used. Such feedback can be conceptualized as a log of past product reviews (e.g., reviews of products offered for sale by an online retailer such as Amazon). Reviewer's opinions change over time, as do products (and candidates). In the context of recruiting, people's skills, education, seniority, work history, and other candidate features can change over time. An embodiment handles these issues by providing a snapshot in the past time at the time of decision making for a given candidate, while also recognizing changes from that past time to the present for other candidates in a next mini-batch of a candidate stream. In an embodiment, this is accomplished by using past recruiting tool log data to train mini-batches or sets of data for candidate streams. By using past data for training, reviews or feedback regarding candidates can contribute to a current candidate stream. This is akin to using past data regarding reviews of online videos (e.g., reviews of videos available via an online video system) that remain available online even though the reviewers opinions may change over time.

By using past log data to train models and ranking algorithms used in a streaming environment, embodiments enable recruiting tool log files created in the past (before such a streaming environment existed) to be used as a proxy for past candidate streams.

Embodiments repurpose past recruiter review logs to create a pseudo stream representation. For instance, embodiments take into account that:

(1) Recruiter and hiring manager are both acting rationally.

(2) A recruiter sends a set of candidates for review (i.e., a mini-batch) and may receive a label on part of the mini-batch.

(3) A rational recruiter will take this feedback into account and modify his/her search behavior to determine the next set of candidates for review.

(4) A sequence of mini-batch requests translates into a stream, and such a dataset can be used to train ranking algorithms for automated sourcing.

Embodiments provide the following capabilities:

(a) Techniques for partitioning candidate stream data into training, validation and test datasets.

(b) Techniques for label generation based on feedback labels. For example, methods generate labels based on text in feedback. In some embodiments, labels are approximately the same as for explicit feedback (e.g., acceptance, rejection, or deferral of a candidate).

(c) Techniques for attribution of weights to specific attributes in member profiles by using textual annotations provided by a decision maker (e.g., a hiring manager). These techniques can include re-weighting based on log information.

(d) Attribution technique for a user's (e.g., a recruiter's) search queries that resulted in items being saved to a staffing or recruiting project. Such items may be saved between creations of mini batches. This technique can include analysis of intent evolution. For example, a timeline can include a first mini-batch being sent to a user (e.g., a recruiter) where the user made a certain set of searches. In this example, the user can save a member profile of interest and/or send an email to the member corresponding to the profile). Here, the attribution technique determines the recruiter's intent (e.g., searching for a software developer in a particular city), and for each candidate (member profile) added to a stream, identify what was the query utilized which resulted in that inclusion of the member (e.g., a software developer in the particular city). Embodiments use log data to infer what the recruiter learned from that past interaction, and add more candidates based on that query. This can be implemented as either a query change that resulted in more candidates the recruiter liked, or no change in the query based on analyzing the log data to determine that the recruiter accepted many candidates that were presented.

Embodiments overcome staleness issues that can arise from using log data. For example, considering cases where the recruiter review data dates back multiple years (e.g., 2-10 years), an example technique repurposes historical data by taking into account the following issues.

1. Standardization and Ranking signals on the profiles are bound to have changed.

2. User profiles and careers would have progressed drastically and hence the current state of the member profiles is vastly different from what was seen and reviewed by the recruiter and the manager at a time in years past.

3. Members may have appeared multiple times on a stream in varying capacity and there may be contradictory judgements for the same member profile across different points in time.

To overcome the above-noted issues, an embodiment employs a time machine function or block. In one embodiment, the time machine function can be implemented as a UDF that takes a member's profile and timeline from standardized log or review data and generates a timeline for: position-derived data, and education-derived data. Assuming that most of the member profiles may contain a duration for a position, embodiments provide two functionalities for this UDF:

(1) AsOf(timestamp): This function consumes a member's profile data and provides a snapshot of the member profile as of a certain day in the past.

(2) Between(start, end): This function produces a member timeline as specified by the two epochs.

Embodiments use datasets derived from log or review data to train online models for feature re-weighting (i.e., re-weighting candidate features). A description of such feature re-weighting based on the datasets follows below.

Embodiments also use the datasets to explore A/B test strategies for candidate streams

Additional or alternative embodiments establish baseline convergence time for streams in an automated sourcing or intelligent matches context.

Explicit feedback can be used to re-weight arms of a multi-armed bandit (MAB), where the MAB solution is used to explore the appropriateness of each of a set of possible user query intents in terms of each intent's match to a current, hidden intent of the user. For instance, each arm of the MAB solution can represent an intent, and the choice of weights for these arms can be determined based on user feedback (e.g., recruiter feedback). In some embodiments, explicit feedback is used to populate arms for an MAB approach. According to these embodiments, the MAB approach is a way to explore whether, for a current candidate search, certain candidate feature weights are more appropriate for the search.

In some embodiments, implicit feedback can include one or more user feedback signals or measurements such as, for example, the user's dwell time on a presented candidate, a number of a member's profile sections viewed by the user, and a number of revisits by the user to a saved member profile. For instance, implicit feedback can use log data from an automated sourcing recruiting tool to measure an amount of things in a member profile a user has reviewed or seen (e.g., a number of profile sections viewed). In this example, such log data from an automated sourcing product can be used to determine if a user interested in particular skill set, seniority or tenure in a position, seniority or tenure at an organization, and other implicit feedback that can be determined from log data.

Embodiments incorporate the above-noted types of explicit and implicit feedback signals into a weighted scheme of signals. This single weighted scheme of signals is used as a correlation between the explicit and implicit feedback to develop attribution schemes for determining relative weights of urns on a member profile. In additional or alternative embodiments, the explicit member urns feedback is used to identify ranking and recall limitations of previously displayed member profiles and to devise reformulation schemes for query intent clusters. The query intent clusters do not require displaying a query for editing by the user. Instead, the user's query can be tuned automatically behind the scenes. For instance, query intent clusters can be used to automatically reformulate and tune a query based on a mixture of explicit and implicit feedback as the user is looking for candidates, and reviews, selects, defers, or rejects candidates in a candidate stream. As used herein, the terms ‘stream of candidates’ and ‘candidate stream’ generally refer to sets of candidates that can be presented or displayed to a user. The user can be a user of an automated sourcing recruiting tool. For example, the user can be a recruiter or a hiring manager that interacts with a recruiting tool to view and review a stream of candidates being considered for a position or job.

The above-noted types of explicit and implicit feedback can be used to promote and demote candidates by re-weighting candidate features. That is, values assigned to weights corresponding to candidate features (e.g., suggested candidate features) can be re-calculated or re-weighted. Some feedback can conflict with other feedback. For example, seniority feedback can indicate that a user wants a candidate with long seniority at a start-up company, but relatively shorter seniority at a larger organization (e.g., a Fortune 500 company). Embodiments provide valuation or ranking of candidates in a stream of candidates. For example, embodiments can present members with member urns that are similar to a suggested candidate, but after user has rejected a threshold number of candidates in a stream.

Instead of requiring large amounts of explicit user feedback, automated sourcing and intelligent matching techniques infer criteria with features and information derived from the user's company or organization, job descriptions, other companies or organizations in similar industries, and implicit user feedback (e.g., feedback inferred based on recent hires). Among many features or factors that can contribute to the criteria for including members of an online system such as a social network system in a stream of candidates, embodiments use a standardized job title and location to start a stream. In some embodiments, the online system hosts a social networking service. In certain embodiments, the social networking service is an online professional network. As a user is fed a stream of candidates, the user can assess respective ones of the candidates. This interaction information can be fed back into a relevance engine that includes logic for determining which candidates end up in a stream In this way, automated sourcing techniques continue to improve the stream.

In certain embodiments, a user of an automated sourcing recruiting tool can create a new stream from a standardized title and location combination. In the event that the user does have a company that is standardized, and the tool has enough data on the organization or company to make it useful, an embodiment can also implicitly leverage the organization's or company's industry and other metadata to improve the immediate quality of the stream. For each new stream, a standardized title and location are used to frame the position. The search service can use the recruiting tool's suggested titles and locations to automatically broaden the search. That is, the title and location used to frame the stream are the job title the candidate will have and the location where they will work, as opposed to requiring the user to enter current titles.

It should be noted that the term ‘ideal’ as used throughout the present disclosure is not intended to be any sort of measurement of desirability of a candidate. Rather, a candidate is simply labeled as ‘ideal’ if a searcher has specified the candidate as a basis for the search. In other words, if the searcher feels that the candidate is ideal enough to specify as a basis for the search, then that is enough for the candidate to be considered ideal for the systems and methods described herein. There is no necessity that that the candidate actually ‘be’ ideal, nor any measurement of how ideal a candidate is.

FIG. 1 is a block diagram illustrating a client-server system 100, in accordance with an example embodiment. A networked system 102 provides server-side functionality via a network 104 (e.g., the Internet or a wide area network (WAN)) to one or more clients. FIG. 1 illustrates, for example, a web client 106 (e.g., a browser) and a programmatic client 108 executing on respective client machines 110 and 112.

An application program interface (API) server 114 and a web server 116 are coupled to, and provide programmatic and web interfaces respectively to, one or more application servers 118. The application server(s) 118 host one or more applications 120. The application server(s) 118 are, in turn, shown to be coupled to one or more database servers 124 that facilitate access to one or more databases 126. While the application(s) 120 are shown in FIG. 1 to form part of the networked system 102, it will be appreciated that, in alternative embodiments, the application(s) 120 may form part of a service that is separate and distinct from the networked system 102.

Further, while the client-server system 100 shown in FIG. 1 employs a client-server architecture, the present disclosure is, of course, not limited to such an architecture, and could equally well find application in a distributed, or peer-to-peer, architecture system, for example. The various applications 120 could also be implemented as standalone software programs, which do not necessarily have networking capabilities.

The web client 106 accesses the various applications 120 via the web interface supported by the web server 116. Similarly, the programmatic client 108 accesses the various services and functions provided by the application(s) 120 via the programmatic interface provided by the API server 114.

FIG. 1 also illustrates a third party application 128, executing on a third party server 130, as having programmatic access to the networked system 102 via the programmatic interface provided by the API server 114. For example, the third party application 128 may, utilizing information retrieved from the networked system 102, support one or more features or functions on a website hosted by a third party. The third party website may, for example, provide one or more functions that are supported by the relevant applications 120 of the networked system 102.

In some embodiments, any website referred to herein may comprise online content that may be rendered on a variety of devices including, but not limited to, a desktop personal computer (PC), a laptop, and a mobile device (e.g., a tablet computer, smartphone, etc.). In this respect, any of these devices may be employed by a user to use the features of the present disclosure. In some embodiments, a user can use a mobile app on a mobile device (any of the machines 110, 112 and the third party server 130 may be a mobile device) to access and browse online content, such as any of the online content disclosed herein. A mobile server (e.g., API server 114) may communicate with the mobile app and the application server(s) 118 in order to make the features of the present disclosure available on the mobile device.

In some instances, the networked system 102 is an online system, such as, for example, a social network system. In certain embodiments, the networked system 102 may host a social networking service.

FIG. 2 is a block diagram illustrating components of an online system 210 (e.g., a social network system hosting a social networking service), according to some example embodiments. The online system 210 is an example of the networked system 102 of FIG. 1. In some embodiments, the online system 210 may be implemented as a social network system. As shown in FIG. 2, the online system 210 can include a data processing block referred to herein as a search engine 216, for use in generating and providing search results for a search query, consistent with some embodiments of the present disclosure. In some embodiments, the search engine 216 may reside on the application server(s) 118 in FIG. 1. However, it is contemplated that other configurations are also within the scope of the present disclosure.

As shown in FIG. 2, a front end may comprise a user interface block (e.g., a web server 116) 212, which receives requests from various client computing devices, and communicates appropriate responses to the requesting client devices. For example, the user interface block(s) 212 may receive requests in the form of Hypertext Transfer Protocol (HTTP) requests or other web-based API requests. In addition, a member interaction detection block 213 may be provided to detect various interactions that members have with different applications 120, services, and content presented. As shown in FIG. 2, upon detecting a particular interaction, the member interaction detection block 213 logs the interaction, including the type of interaction and any metadata relating to the interaction, in a member activity and behavior database 222.

An application logic layer may include one or more various application server blocks 214, which, in conjunction with the user interface block(s) 212, generate various user interfaces (e.g., web pages) with data retrieved from various data sources in a data layer. In some embodiments, individual application server blocks 214 are used to implement the functionality associated with various applications 120 and/or services provided by the social networking service.

As shown in FIG. 2, the data layer may include several databases, such as a profile database 218 for storing profile data, including both member profile data and profile data for various organizations (e.g., companies, schools, etc.). Consistent with some embodiments, when a person initially registers to become a member of the social networking service, the person will be prompted to provide some personal information, such as his or her name, age (e.g., birthdate), gender, interests, contact information, home town, address, spouse's and/or family members' names, educational background (e.g., schools, majors, matriculation and/or graduation dates, etc.), employment history, skills, professional organizations, and so on. This information is stored, for example, in the profile database 218. Similarly, when a representative of an organization initially registers the organization with the social networking service, the representative may be prompted to provide certain information about the organization. This information may be stored, for example, in the profile database 218, or another database (not shown). In some embodiments, the profile data may be processed (e.g., in the background or offline) to generate various derived profile data. For example, if a member has provided information about various job titles that the member has held with the same organization or different organizations, and for how long, this information can be used to infer or derive a member profile attribute indicating the member's overall seniority level, or seniority level within a particular organization. In some embodiments, importing or otherwise accessing data from one or more externally hosted data sources may enrich profile data for both members and organizations. For instance, with organizations in particular, financial data may be imported from one or more external data sources and made part of an organization's profile. This importation of organization data and enrichment of the data will be described in more detail later in this document.

Once registered, a member may invite other members, or be invited by other members, to connect via the social networking service. A ‘connection’ may constitute a bilateral agreement by the members, such that both members acknowledge the establishment of the connection. Similarly, in some embodiments, a member may elect to ‘follow’ another member. In contrast to establishing a connection, the concept of ‘following’ another member typically is a unilateral operation and, at least in some embodiments, does not require acknowledgement or approval by the member that is being followed. When one member follows another, the member who is following may receive status updates (e.g., in an activity or content stream) or other messages published by the member being followed, or relating to various activities undertaken by the member being followed. Similarly, when a member follows an organization, the member becomes eligible to receive messages or status updates published on behalf of the organization. For instance, messages or status updates published on behalf of an organization that a member is following will appear in the member's personalized data feed, commonly referred to as an activity stream or content stream In any case, the various associations and relationships that the members establish with other members, or with other entities and objects, are stored and maintained within a social graph in a social graph database 220.

As members interact with the various applications 120, services, and content made available via the social networking service, the members' interactions and behavior (e.g., content viewed, links or buttons selected, messages responded to, etc.) may be tracked, and information concerning the members' activities and behavior may be logged or stored, for example, as indicated in FIG. 2, by the member activity and behavior database 222. This logged activity information may then be used by the search engine 216 to determine search results for a search query.

In some embodiments, the databases 218, 220, and 222 may be incorporated into the database(s) 126 in FIG. 1. However, other configurations are also within the scope of the present disclosure.

Although not shown, in some embodiments, the online system 210 provides an API module via which applications 120 and services can access various data and services provided or maintained by the social networking service. For example, using an API, an application may be able to request and/or receive one or more navigation recommendations. Such applications 120 may be browser-based applications 120, or may be operating system-specific. In particular, some applications 120 may reside and execute (at least partially) on one or more mobile devices (e.g., phone or tablet computing devices) with a mobile operating system. Furthermore, while in many cases the applications 120 or services that leverage the API may be applications 120 and services that are developed and maintained by the entity operating the social networking service, nothing other than data privacy concerns prevents the API from being provided to the public or to certain third parties under special arrangements, thereby making the navigation recommendations available to third party applications 128 and services.

Although the search engine 216 is referred to herein as being used in the context of a social networking service, it is contemplated that it may also be employed in the context of any website or online services. Additionally, although features of the present disclosure are referred to herein as being used or presented in the context of a web page, it is contemplated that any user interface view (e.g., a user interface on a mobile device or on desktop software) is within the scope of the present disclosure.

In an example embodiment, when member profiles are indexed, forward search indexes are created and stored. The search engine 216 facilitates the indexing and searching for content within the social networking service, such as the indexing and searching for data or information contained in the data layer, such as profile data (stored, e.g., in the profile database 218), social graph data (stored, e.g., in the social graph database 220), and member activity and behavior data (stored, e.g., in the member activity and behavior database 222). The search engine 216 may collect, parse, and/or store data in an index or other similar structure to facilitate the identification and retrieval of information in response to received queries for information. This may include, but is not limited to, forward search indexes, inverted indexes, N-gram indexes, and so on.

FIG. 3 is a block diagram illustrating the application server block 214 of FIG. 2 in more detail. While in many embodiments the application server block 214 will contain many subcomponents used to perform various different actions within the online system 210, in FIG. 3 only those components that are relevant to the present disclosure are depicted. Here, a server profile search component 300 works in conjunction with a client profile search component 302 to perform one or more searches on member profiles stored in, for example, profile database 218. The server profile search component 300 may be, for example, part of a larger software service that provides various functionality to employers or recruiters. The client profile search component 302 may include a user interface and may be located on a client device. For example, the client profile search component 302 may be located on a searcher's mobile device or desktop/laptop computer. In some example embodiments, the client profile search component 302 may itself be, or may be a part of, a standalone software application on the client device. In other example embodiments, the client profile search component 302 is a web page and/or web scripts that are executed inside a web browser on the client device. Regardless, the client profile search component 302 is designed to accept input from the searcher and to provide visual output to the searcher.

In an example embodiment, the input from the client profile search component 302 includes an identification of one or more suggested candidates for a job opening. This identification may be accomplished in many ways. In some example embodiments, the input may be an explicit identification of one or more member profiles stored in the profile database 218. This explicit identification may be determined by the searcher, for example, browsing or otherwise locating specific profiles that the searcher feels are ideal. For example, the searcher may know the identity of individuals on a team in which the open position is available, and may navigate to and select the profiles associated with those team individuals In another example embodiment, the searcher may create one or more hypothetical ‘suggested candidate’ profiles and use those as the input In another example embodiment, the searcher may browse or search profiles in the profile database 218 using traditional browsing or searching techniques In some example embodiments the explicit identification may be provided by the job poster.

The server profile search component 300 may contain an attribute extractor 304. The attribute extractor 304 may be implemented as a system component, block, or module that is configured to extract one or more attributes from one or more profiles of one or more suggested candidates (i.e., one or more suggested candidate profiles). For instance, the attribute extractor 304 may be configured to extract attributes, including, for example, skills, companies, titles, schools, industries, etc., from the profiles of the one or more current candidate profiles. In the example of FIG. 3, the attribute extractor 304 extracts raw attributes, such as, for example, skills, companies, titles, schools, industries, etc., from the profiles of the one or more suggested candidates. These raw attributes are then passed to a query builder 306. For each attribute type, the query builder 306 aggregates the raw attributes across the input candidates, expands them to similar attributes, and finally selects the top attributes that best represent the suggested candidates.

After the query is generated, in an example embodiment the generated query may be shown to the searcher via the client profile search component 302 and the searcher may have the opportunity to edit the generated query. This may include adding to or removing some attributes, such as skills and companies, in the query. As part of this operation, a query processor 308 may perform a search on the query and present raw results to the searcher via the client profile search component 302. These raw results may be useful to the searcher in determining how to edit the generated query.

In an example embodiment, a machine learning model is trained to make ‘smart suggestions’ to the searcher as to how to modify the generated query. The model may be trained to output suggestions based on any number of different facets, such as title, company or organization, industry, location, school, and skill. According to embodiments, such training of a machine learning model is performed using historical log data.

Usage data can be gathered regarding actions taken by searchers when facing a suggestion—(1) add the suggestion, (2) delete the suggestion, or (3) ignore the suggestion. Intuitively, if a searcher adds a suggestion it is probably a desired one and thus can be considered a positive training sample. If the searcher deletes the suggestion it is probably not a desired one, and thus can be considered a negative training sample. For ignored suggestions, if the suggestion is positioned lower than an added suggestion (e.g. ‘Santa Clara University’ is positioned lower than added ‘University of California, Santa Cruz’), then it is not certain whether the suggestion is really ignored by searchers or useless in the setting of the query. Thus, this data can be ignored. If, however, the ignored suggestion is positioned higher than an added suggestion, it can be treated as negative data.

After the query is modified, the query processor 308 may refresh the search results. A search results ranker 310 may act to rank the search results, taking into account both the query (including potentially the generated query and the modified generated query) as well as the input suggested candidates when ranking the search results.

Referring back to the query builder 306, given the raw attributes from the profiles of the suggested candidates, the query builder 306 generates a query containing skills, companies, titles, etc. that best represents the suggested candidates.

The query builder 306 may comprise a skills generator 312 designed to generate skills to be added to the generated query. The social networking service may allow members to add skills to their profiles. Typical examples of skills that, for example, an information technology (IT) recruiter might search could be ‘search,’ ‘information retrieval,’ ‘machine learning.’ etc. Members may also endorse skills of other members in their network by, for example asserting that the member does indeed have the specified skills. Thus, skills may be an important part of members' profiles that showcase their professional expertise. A technical challenge encountered, however, is that suggested candidates may not explicitly list all of the skills they have on their profiles. Additionally, some of their skills may not be relevant to their core expertise. For example, an IT professional may list ‘nonprofit fundraising’ as a skill.

To overcome these challenges, expertise scores for the suggested candidate may be estimated based on explicit skills (skills the member has explicitly listed) as well as implicit skills (skills the member is likely to have, but has not explicitly linked).

FIG. 4 is a block diagram illustrating the skills generator 312 in more detail, in accordance with an example embodiment. As shown in FIG. 4, a scoring apparatus 400 may calculate a set of expertise scores 402 using a statistical model 404 and a set of candidate features 406-408 for candidate member profiles. Candidate features 406-408 may be aggregated into a data repository 410 from the member profiles and/or user actions. For example, candidate features 406-408 may be received from a number of servers and/or data centers associated with the websites and/or applications and stored in a relational database for subsequent retrieval and use.

Prior to calculating expertise scores 402 on actual member profiles, a training apparatus 412 may obtain training data for statistical model 404, which includes a positive class 414 and a negative class 416. Positive class 414 may include data associated with items of a particular category (e.g., trait, attribute, dimension, etc.), while negative class 416 may include data associated with items that do not belong in the category. According to embodiments, such training data can be based on historical log or review data.

For example, statistical model 404 may be a logistic regression model that classifies each member profile as either an expert or a non-expert in a corresponding skill. Positive class 414 may thus include a subset of candidate features 406-408 associated with members with known expertise in one or more skills. Such ‘expert’ members may be identified based on publications, speeches, awards, and/or contributions of the users in their respective fields. On the other hand, negative class 416 may include a subset of candidate features 406-408 associated with members who are not recognized as experts in their respective fields, such as random members who list a given skill in their profiles. Because far fewer users belong in positive class 414 than negative class 416, positive class 414 may be oversampled to produce a roughly class-balanced set of training data for statistical model 404.

Next, training apparatus 412 may use positive class 414 and negative class 416 to train statistical model 404. For example, training apparatus 412 may use maximum-likelihood estimation (MLE) and/or another estimation technique to estimate the parameters of a logistic regression model for calculating expertise scores 402. After training of the logistic regression model is complete, the parameters may be set so that the logistic regression model outputs values close to 1 for training data in positive class 414 and values close to 0 for training data in negative class 416. According to embodiments, the training apparatus 412 may use historical log data or review data from a recruiting tool or product.

The trained statistical model 404 may be provided to scoring apparatus 400, which calculates expertise scores 402 for member profiles not included in the training data (such as ideal member profiles supplied by the searcher) by applying statistical model 404 to candidate features (e.g., candidate features 406-408) for each of the items. For example, a feature vector may be generated for each item from a subset of candidate features 406-408 in data repository 410, and statistical model 404 may be applied to the feature vector to calculate an expertise score for the item with respect to a dimension of the member profile.

Candidate features 406-408 used in the calculation of expertise scores 402 may include demographic features, social features, and behavioral features. Demographic features may include data related to a user's location, age, experience, education, and/or background; social features may include features related to the behavior of other users with respect to the user; and behavioral features may include features related to the user's actions or behavior with the online professional network and/or related websites or applications.

FIG. 5 is a diagram illustrating an offline process 500 to estimate expertise scores, in accordance with another example embodiment. A supervised machine learning algorithm combines various signals 502, such as skill-endorsement graph page rank, skill-profile textual similarity, member seniority, etc. to estimate the expertise score. After this step, a formed expertise matrix 504 is very sparse since only a small percentage of the pairs can be predicted with any degree of certainty. Expertise matrix 504 may be factorized into member matrix 506 and skill matrix 508 in K-dimensional latent space. Then, the dot-product of the expertise matrix 504 and skill matrix 508 is computed to fill in the ‘unknown’ cells. The intuition is that the more members who list two particular skills in their corresponding member profiles (called co-occurrence of skills), the more likely it is that a member only listing one of those skills also has the other skill as a latent skill. Since the dot-product results in a large number of non-zero scores of each member on the skills, the scores can then be thresholded such that if the member's score on a skill is less than a particular threshold, the member is assumed not to know the skill and is assigned a zero expertise score on the skill. Thus, the final expertise matrix 510 is still sparse, but relatively much denser than formed expertise matrix 504.

Turning now to organizations such as companies, for a particular company, given the recent hire profiles, the query builder 306 can generate a set of other companies, outside of the particular company, that are likely to have candidates similar to the particular company's recent hires in their recent hire profiles. In order to accomplish this, the query builder 306 contains an organization generator 314, which uses collaborative filtering to find organization relationships. Specifically, an organization browse map using co-viewing relationships (people who view organization A and also view organization B) may be utilized. Intuitively, organizations co-viewed by highly overlapped sets of people are likely to be similar. Thus, activity and/or usage information for searchers/browsers within the social networking service may be retrieved and mined to construct the organization browse map, and this browse map may then be used to find the organization relationships by the organization generator 314. Other information may be used either in conjunction with or in lieu of the organization browse map. For example, the social networking service may keep track of candidates that apply to a given organization. Therefore, it may deduce that if a user who applied to organization B also applied to organization A, then organization A and organization B are similar. This similarity relationship may be used like the browse map is used to generate organizations related to organizations identified in profiles of suggested candidates. Another signal that may be used is organization movement, meaning that if a large number of people who left organization A went to work for organization B, this might imply that organization A and organization B are somewhat similar.

Similar strategies can be used for other facets of a query. For example, title, industry, locations, and schools can all be expanded from those facets in the idea candidate profiles by finding similar facets using, for example, browse maps.

Once the query builder 306 completes building the query based on the techniques described above, the query may be submitted to a search engine to return search results. The hope, of course, is that the search results represent candidates who are similar in some ways to the suggested candidates submitted by the searcher, thus alleviating the searcher of the burden of composing the query. Once the results are returned, a search results ranker 310 may rank the search results according to one or more ranking algorithms. A subset of the top ranked search results may then be displayed to the searcher using a results display component 316. In an example embodiment, the results display component 316 interacts with the client profile search component 302 to facilitate such a display. The number of top ranked search results displayed may vary based on, for example, current size of a display window, font size, user preferences, etc.

While any ranking algorithms may be used by the search results ranker 310 to rank the search results, in an example embodiment, a machine learning algorithm is used to train a ranking model specifically to be used with searches generated by searchers providing suggested candidates in lieu of text-based keywords. Given the significant difference between a search by suggested candidates and a traditional query-based search, this algorithm helps provide rankings that accommodate this new type of search. In some embodiments, log or review data from a recruiting tool is used to train the ranking model.

FIG. 6 is a block diagram illustrating the search results ranker 310 in more detail, in accordance with an example embodiment. The search query that produced the search results, as well as the search results, may be fed to a query-based feature producer 600, which produces a set of query-based features 602 of the results. Query-based features 602 include search engine features such as term frequency-inverse document frequency (TF-IDF), term location in document, bag-of-words, etc. These query-based features 602 may be fed to a query-based ranking model 604, which returns scores for each of the query/result pairs.

Separately, a suggested candidate (SC)-based feature producer 606 receives as input the specified suggested candidate(s) and the search results from the query generated by the suggested candidate(s). The suggested candidate (SC)-based feature producer 606 then produces a set of suggested candidate-based features 608 of the results. Suggested candidate-based features 608 include features that are based on a comparison of suggested candidates and the search results (each feature measures one suggested candidate/search result pair). Example candidate-based features include similar career path, skill similarity, headline matching, headline similarity, and browsemap similarity.

Similar career path is a measure of a trajectory similarity between the positions held by the suggested candidate and the search result. Thus, for example, if the suggested candidate started as an intern, was promoted to a staff engineer, and then was promoted to project manager, a search result having a similar progression of the trajectory of their career path would rank higher in this feature than, for example, a search result who started off at the top (e.g., as a project manager). To capture the trajectory information, each member profile may be modeled as a sequence of nodes, each of which records all information within a particular position of a member's career, such as company or organization, title, industry, time duration, and keyword summary.

Headline matching is a measure of the similarity between the query and the headline of each result. Notably, this is based on a text-based comparison, and is not strictly suggested candidate-based. A headline is one or more visible fields (along with name) displayed as a search result snippet for a search result. While the concept of creating snippets for each search result is a topic that is beyond the scope of the present disclosure, such snippets often include a headline that helps explain why the result is relevant and likely to trigger actions from the searcher. The headline matching feature, therefore, measures the similarity between the query and this headline from the search result's snippet.

Headline similarity is a measure of the similarity between a headline of the suggested candidate and the headline of the search result. This similarity calculation may be performed with or without considering word semantics. In example embodiments where word semantics are not considered, a word2vec algorithm may be utilized. Word2vec is a group of related models used to produce word-embeddings. The word-embeddings are shallow, two-layer neural networks that are trained to reconstruct linguistic contexts of words. The neural network is shown a word and guesses which words occurred in adjacent position in an input text. After training, word2vect models can be used to map each word to a vector of typically several hundred elements, which represent that word's relation to other words.

Browsemap similarity is a measure of whether and how much other members/searchers/browsers visited both the suggested candidate's profile and the search result's profile in the same browsing session. The intuition is that if previous members/searchers/browsers viewed both profiles in the same session, then there is a higher likelihood that the profiles are similar, and thus that the underlying suggested candidate and search result are similar.

The suggested candidate-based features 608 may be fed along with the scores from the query-based ranking model 604 to a machine learning algorithm 610. The machine learning algorithm 610 is designed to train a combined ranking model 612 that is capable of determining a ranking score for a search result at runtime. This training may use labels supplied for training data (e.g., training suggested candidates and training search results along with labeled scores for each). In certain embodiments, log or review data from a recruiting tool is used to train the combined ranking model 612.

The training may involve the machine learning algorithm 610 learning which features/scores are more or less relevant to the ranking scores (including ranking scores from log data), and appropriately weighting such features and scores for runtime computations. At runtime, a feature extractor 614 extracts both query-based and suggested candidate-based features from the query, search results, and suggested candidates and feeds these features to the combined ranking model 612, which produces the scores as per its model. A ranker 616 then uses these ranking scores to rank the search results for display to the searcher.

Since searching by suggested candidates is a relatively new concept, it is difficult to generate labeled data directly from a log of previous search systems, as would typically be done to generate labeled data. Instead, in an example embodiment, labeled data is generated from the log of a query-based search. One such log is a log of electronic communications performed after the query-based search. For example, if a searcher sees twenty results to a query-based search for candidates, and sends email communications to eight candidates from the twenty results, then it may be assumed that these eight candidates are similar enough to be considered for the same job, and thus if a profile for one or more of those eight candidates had been submitted for a search by suggested candidate, the other candidates could be considered likely top results. In an example embodiment, other actions taken with respect to previous search results may be logged and similarly used to determine suggested candidate matches. For instance, while communication with a candidate (e.g., via an email or a LinkedIn InMail message) may be considered as strongly indicative of a match for the underlying position (and thus a match with other candidates also emailed for the same position) and assigned a high relevance score, clicking on a candidate (without an email) may be considered to be a partial match and may be assigned a moderate relevance score, while skipped results might be considered a low relevance score. The relevance scores may be used as the labels for the sample data.

Thus, in certain example embodiments, communications between searchers and members of the online system (e.g., an online system hosting a social network service) are monitored and logged and these communications are used to derive a label score for each sample search result/suggested candidate pair (the sample search results may simply be the search results presented in response to previous queries). The label score may be generated using various combinations of the metrics described above. For instance, if the same searcher (e.g., a recruiter or hiring manager) communicated with both candidates A and B in response to the same search query, then candidate B is assigned a score of 5 (on a scale of 1 to 5, 5 being most relevant) for a suggested candidate A and candidate A is assigned a score of 5 for a suggested candidate B. Actions such as clicking on a candidate that indicate a moderate relevance may be assigned a score of 3 and no actions may be assigned a score of 1. Scores for various log entries can then be combined and averaged. The result is profile pairs that have been assigned a score of between 1 and 5 based on previous actions or inactions by previous searchers. These label scores may then be used as labels for hypothetical suggested candidate/search result pairs for those same member profiles.

In an example embodiment, a dynamic weight trainer is introduced into the architecture of FIG. 6 in order to dynamically alter the weights assigned to the SC-based features 608. Specifically, a search query need not be limited to a single query and then the search is complete. Often the searcher may interact with the original query and search result to provide additional refinements of the original search. This is true not only with traditional text-based searches but also can be true with suggested candidate-based searches as well. This may be accomplished by the searcher applying additional filters and or making text-based additions to the initial suggested candidate-based search to refine the results. The result is that the role of the suggested candidate-based features, which directly measure the similarity between the suggested candidate(s) and the search results, become less and less important as the search is refined. At the same time, as the search session continues, the confidence of the remaining attributes (e.g., query-based attributes) increase in usefulness.

FIG. 7 is a block diagram illustrating the search results ranker 310 in more detail, in accordance with another example embodiment FIG. 7 is identical to FIG. 6 with the exception of the addition of a dynamic weight trainer 700. The purpose of the dynamic weight trainer 700 is to dynamically alter the weights of the features extracted to favor the query-based features 602 over the suggested candidate-based features 608 over time. This may be performed by applying a decay function, defined on some measure of session length, such as the number of query refinements, to gradually reduce the weights of the suggested candidate-based features 608 and/or increase the weights of the query-based features 602. This function controls the dynamic balance between the impacts of the ideal input candidates and the query on the result ranking. In an embodiment, the dynamic weight trainer 700 can use historical log data or review data from a recruiting tool.

FIG. 8 is a flow diagram illustrating a method 800 for performing a suggested candidate-based search in accordance with an example embodiment. At operation 802, one or more suggested candidate documents may be obtained. In an example embodiment, these documents are member profiles in a social networking service and they are obtained by a searcher specifying the corresponding members and the member profiles being retrieved from a database based on the searcher's specified members. However, implementations are possible where the documents obtained are not member profiles.

At operation 804, one or more query intents are extracted from the one or more suggested candidate documents. At operation 806, results of a search query that is generated based on the extracted one or more attributes are displayed on a display device. As shown, operation 806 can include displaying one or more top-ranked suggested candidate documents on the display device. At operation 808, log data is received and reviewed. As shown, operation 808 can include using review data regarding candidates. At operation 810, weight attribution can be performed based on the log data. As shown, operations 806-810 can be repeated to display updated top-ranked candidate documents based on log data and weight attribution (e.g., re-weighting of candidate features) based on the log data.

FIG. 9 is a flow diagram illustrating generating a search query based on extracted one or more attributes, in accordance with an example embodiment. At operation 900, the one or more attributes are aggregated across the one or more suggested candidate documents. At operation 902, the aggregated one or more attributes are expanded to include similar attributes. At operation 904, top attributes most similar to attributes of all of the one or more suggested candidate documents are selected. At operation 906, a set of expertise scores are calculated using a statistical model and a set of features regarding skills of the one or more candidate documents. The statistical model may be a logistic regression model trained using a machine learning algorithm. As shown in FIG. 9, in an embodiment, the statistical model may be trained using log data or review data. At operation 908, the expertise scores are used to rank skills of the one or more suggested candidate member profiles, using the top attributes. At operation 910, one or more top ranked skills are added to the search query.

At operation 912, a browse map is referenced. At operation 914, one or more companies are added to the search query, the companies being ones who have been co-viewed during the same browsing session as a company or organization identified in one or more of the suggested candidate documents, by using the browse map.

FIG. 10 is a flow diagram illustrating a method 1000 of ranking search results using suggested candidates in accordance with an example embodiment. At operation 1002, one or more suggested candidate documents may be obtained In an example embodiment, these documents are member profiles in a social networking service and they are obtained by a searcher specifying the corresponding members and the member profiles being retrieved from a database based on the searcher's specified members. However, implementations are possible where the documents obtained are not member profiles.

At operation 1004, a search is performed using a search query, resulting one or more result documents. Like with the suggested candidate documents, the result documents may be member profiles in an example embodiment. In one example embodiment, operation 1004 can be performed using some of the operations described above with respect to FIGS. 8 and 9.

At operation 1006, one or more query-based features are produced from the one or more result documents using the search query. As described above, this may include features such as TF-IDF.

At operation 1008, one or more suggested candidate-based features may be produced from the one or more result documents using the one or more suggested candidate documents. As described above, the suggested candidate-based features may include similar career path, skill similarity, headline matching, headline similarity, and/or browsemap similarity.

At operation 1010, the one or more query-based features and the one or more suggested candidate-based features are input to a combined ranking model, outputting ranking scores for each of the one or more result member profiles. The combined ranking model may be trained using similar query-based and suggested candidate-based features from sample result documents as well as sample search queries and labels. As illustrated in FIG. 10, in some embodiments, the combined ranking model may be trained using log data or review data.

At operation 1012, the one or more result documents are ranked based on the ranking score. At operation 1014, display of the one or more top ranked result documents on a computer display is caused.

FIG. 11 is a flow diagram illustrating a method 1100 for generating labels for sample suggested candidate member profiles in accordance with an example embodiment. At operation 1102, one or more sample suggested candidate member profiles in an online system (e.g., an online system hosting a social networking service) are obtained. At operation 1104, one or more sample search result member profiles in the social networking service are obtained.

At operation 1106, unique pairs of member profiles are identified. As shown in FIG. 11, operation 1106 comprises identifying the unique pairs such that each unique pair of profiles consists of one of the sample suggested candidate member profiles obtained at operation 1102 and one of the sample search result member profiles obtained at operation 1104.

At operation 1108, for each of the unique pairs of sample suggested member profiles, a label is generated using a score generated from log information of the social networking service. The log information includes records of communications between a searcher and members of the social networking service, the score being higher if the searcher communicated with both the member corresponding to the sample suggested candidate member profile and the member corresponding to the sample search result member profile in a same search session. The log information may include historical review data from log files of the social networking service. The log information may further include records of user input by the searcher (e.g., a recruiter), the user input causing interaction with member profiles in the social networking service but not resulting in communications between the searcher and the member of the social networking service corresponding to both the sample suggested candidate member profile and the sample search result member profile in the same search session. An example includes clicking on member profiles and viewing the member profiles but not emailing the corresponding members. A search session may be defined in a number of different ways. In one example embodiment, a search session is the same as a browsing session (e.g., as long as the searcher is logged in to the social networking service). In another example embodiment, the search session is limited to a period of time between a searcher initiating a search and the searcher submitting an unrelated search or logging off the social networking service.

At operation 1110, the generated labels are inputted or fed into a machine learning algorithm to train a combined ranking model used to output ranking scores for search result member profiles. As shown in FIG. 11, according to some embodiments, the combined ranking model may be trained using log data from a recruiting tool (e.g., historical review data).

FIG. 12 is a flow diagram illustrating a method 1200 of dynamically training weights of a machine learning algorithm model in accordance with an example embodiment. At operation 1202, one or more suggested candidate documents are obtained. At operation 1204, a search is performed using a search query, returning one or more result documents. This search query may or may not have been generated using the one or more suggested candidate documents.

At operation 1206, one or more query-based features are produced from the one or more result documents using the search query. At operation 1208, one or more suggested candidate-based features are produced from the one or more result documents using the one or more suggested candidate documents. At operation 1210, the one or more query-based features and the one or more suggested candidate-based features are input to a combined ranking model. The combined ranking model is trained by a machine learning algorithm to output a ranking score for each of the one or more result documents. The combined ranking model includes weights assigned to each of the one or more query-based features and each of the one or more suggested candidate-based features. As depicted in FIG. 12, according to certain embodiments, the combined ranking model may be trained using historical log data from a recruiting tool (e.g., review data).

At operation 1212, the one or more result documents are ranked based on the ranking scores. At operation 1214, display of one or more top ranked documents on a computer display is caused. At operation 1216, one or more refinements to the search are received. At operation 1218, the weights assigned to each of the one or more query-based features are dynamically trained to increase as more refinements are received, and the weights assigned to each of the one or more suggested candidate-based features are dynamically trained to decrease as more refinements are received. This dynamic training may utilize a decay function based on, for example, time or number of refinements. According to certain embodiments, this dynamic training may also utilize log data or review data from a recruiting tool.

FIG. 13 is a screen capture illustrating a first screen 1300 of a user interface for performing a suggested candidate—based search for candidates in accordance with an example embodiment. The first screen 1300 includes an area 1302 where a searcher can review one or more suggested candidates for the search. As shown, area 1302 can display attributes of the suggested candidates such as the candidates' names and job titles (e.g., positions).

FIG. 14 is a screen capture illustrating a second screen 1400 of the user interface for performing a suggested candidate—based candidate search, in accordance with an example embodiment. The second screen 1400 presents results 1402 of the search, as well as displaying the query generated using the specified suggested candidates. For example, the query terms 1404, 1406, and 1408 used for the search are displayed in the second screen 1400. The query may be displayed by highlighting terms of the query in various categories. In the example of FIG. 14, a job title 1404 indicates that ‘software engineer’ is a job title term that was generated for the query, a skill 1406 indicates that ‘python’ is a skill term that was generated for the query, and an industry 1408 indicates that ‘Internet’ is an industry term that was generated for the query. The searcher can then easily modify the query by adding additional terms to the query and/or removing some of the identified terms that had been previously generated.

Blocks, Components, and Logic

Certain embodiments are described herein as including logic or a number of blocks, components, modules, or mechanisms. Blocks may constitute machine components implemented as a combination of software modules (e.g., code embodied on a machine-readable medium) and hardware modules. A ‘hardware module’ is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various example embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware modules of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware module that operates to perform certain operations as described herein.

In some embodiments, a hardware module may be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware module may include dedicated circuitry or logic that is permanently configured to perform certain operations. For example, a hardware module may be a special-purpose processor, such as a Field-Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC). A hardware module may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware module may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, hardware modules become specific machines (or specific components of a machine) uniquely tailored to perform the configured functions and are no longer general-purpose processors. It will be appreciated that the decision to implement a hardware module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

Accordingly, the phrase ‘hardware module’ should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. As used herein, ‘hardware-implemented module’ refers to a hardware module. Considering embodiments in which hardware modules are temporarily configured (e.g., programmed), each of the hardware modules need not be configured or instantiated at any one instance in time. For example, where a hardware module comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware modules) at different times. Software accordingly configures a particular processor or processors, for example, to constitute a particular hardware module at one instance of time and to constitute a different hardware module at a different instance of time.

Hardware modules can provide information to, and receive information from, other hardware modules. Accordingly, the described hardware modules may be regarded as being communicatively coupled. Where multiple hardware modules exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware modules. In embodiments in which multiple hardware modules are configured or instantiated at different times, communications between such hardware modules may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware modules have access. For example, one hardware module may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware module may then, at a later time, access the memory device to retrieve and process the stored output. Hardware modules may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information).

The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more operations or functions described herein. As used herein, ‘processor-implemented module’ refers to a hardware module implemented using one or more processors.

Similarly, the methods described herein may be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented modules. Moreover, the one or more processors may also operate to support performance of the relevant operations in a ‘cloud computing’ environment or as a ‘software as a service’ (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an API).

The performance of certain of the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processors or processor-implemented modules may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the processors or processor-implemented modules may be distributed across a number of geographic locations.

Machine and Software Architecture

The blocks, modules, methods, applications, and so forth described in conjunction with FIGS. 1-14 are implemented in some embodiments in the context of a machine and an associated software architecture. The sections below describe representative software architecture(s) and machine (e.g., hardware) architecture(s) that are suitable for use with the disclosed embodiments.

Software architectures are used in conjunction with hardware architectures to create devices and machines tailored to particular purposes. For example, a particular hardware architecture coupled with a particular software architecture will create a mobile device, such as a mobile phone, tablet device, or so forth. A slightly different hardware and software architecture may yield a smart device for use in the ‘internet of things,’ while yet another combination produces a server computer for use within a cloud computing architecture. Not all combinations of such software and hardware architectures are presented here, as those of skill in the art can readily understand how to implement the inventive subject matter in different contexts from the disclosure contained herein.

Software Architecture

FIG. 15 is a block diagram 1500 illustrating a representative software architecture 1502, which may be used in conjunction with various hardware architectures herein described FIG. 15 is merely a non-limiting example of a software architecture, and it will be appreciated that many other architectures may be implemented to facilitate the functionality described herein. The software architecture 1502 may be executing on hardware such as a machine 1600 of FIG. 16 that includes, among other things, processors 1610, memory/storage 1630, and I/O components 1650. A representative hardware layer 1504 is illustrated and can represent, for example, the machine 1600 of FIG. 16. The representative hardware layer 1504 comprises one or more processing units 1506 having associated executable instructions 1508. The executable instructions 1508 represent the executable instructions of the software architecture 1502, including implementation of the methods, modules, and so forth of FIGS. 1-14. The hardware layer 1504 also includes memory and/or storage modules 1510, which also have the executable instructions 1508. The hardware layer 1504 may also comprise other hardware 1512, which represents any other hardware of the hardware layer 1504, such as the other hardware illustrated as part of the machine 1600.

In the example architecture of FIG. 15, the software architecture 1502 may be conceptualized as a stack of layers where each layer provides particular functionality. For example, the software architecture 1502 may include layers such as an operating system 1514, libraries 1516, frameworks/middleware 1518, applications 1520, and a presentation layer 1544. Operationally, the applications 1520 and/or other components within the layers may invoke API calls 1524 through the software stack and receive responses, returned values, and so forth, illustrated as messages 1526, in response to the API calls 1524. The layers illustrated are representative in nature and not all software architectures have all layers. For example, some mobile or special purpose operating systems may not provide a layer of frameworks/middleware 1518, while others may provide such a layer. Other software architectures may include additional or different layers.

The operating system 1514 may manage hardware resources and provide common services. The operating system 1514 may include, for example, a kernel 1528, services 1530, and drivers 1532. The kernel 1528 may act as an abstraction layer between the hardware and the other software layers. For example, the kernel 1528 may be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, and so on. The services 1530 may provide other common services for the other software layers. The drivers 1532 may be responsible for controlling or interfacing with the underlying hardware. For instance, the drivers 1532 may include display drivers, camera drivers, Bluetooth® drivers, flash memory drivers, serial communication drivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers, audio drivers, power management drivers, and so forth depending on the hardware configuration.

The libraries 1516 may provide a common infrastructure that may be utilized by the applications 1520 and/or other components and/or layers. The libraries 1516 typically provide functionality that allows other software modules to perform tasks in an easier fashion than by interfacing directly with the underlying operating system 1514 functionality (e.g., kernel 1528, services 1530, and/or drivers 1532). The libraries 1516 may include system libraries 1534 (e.g., C standard library) that may provide functions such as memory allocation functions, string manipulation functions, mathematic functions, and the like. In addition, the libraries 1516 may include API libraries 1536 such as media libraries (e.g., libraries to support presentation and manipulation of various media formats such as MPEG4, H.264, MP3, AAC, AMR, JPG, PNG), graphics libraries (e.g., an OpenGL framework that may be used to render 2D and 3D graphic content on a display), database libraries (e.g., SQLite that may provide various relational database functions), web libraries (e.g., WebKit that may provide web browsing functionality), and the like. The libraries 1516 may also include a wide variety of other libraries 1538 to provide many other APIs to the applications 1520 and other software components/modules.

The frameworks 1518 (also sometimes referred to as middleware) may provide a higher-level common infrastructure that may be utilized by the applications 1520 and/or other software components/modules. For example, the frameworks 1518 may provide various graphic user interface (GUI) functions, high-level resource management, high-level location services, and so forth. The frameworks 1518 may provide a broad spectrum of other APIs that may be utilized by the applications 1520 and/or other software components/modules, some of which may be specific to a particular operating system or platform.

The applications 1520 include built-in applications 1540 and/or third party applications 1542. Examples of representative built-in applications 1540 may include, but are not limited to, a contacts application, a browser application, a book reader application, a location application, a media application, a messaging application, and/or a game application. The third party applications 1542 may include any of the built-in applications 1540 as well as a broad assortment of other applications. In a specific example, the third party application 1542 (e.g., an application developed using the Android™ or iOS™ software development kit (SDK) by an entity other than the vendor of the particular platform) may be mobile software running on a mobile operating system such as iOS™, Android™, Windows® Phone, or other mobile operating systems. In this example, the third party application 1542 may invoke the API calls 1524 provided by the mobile operating system such as the operating system 1514 to facilitate functionality described herein.

The applications 1520 may utilize built-in operating system 1514 functions (e.g., kernel 1528, services 1530, and/or drivers 1532), libraries 1516 (e.g., system libraries 1534, API libraries 1536, and other libraries 1538), and frameworks/middleware 1518 to create user interfaces to interact with users of the system. Alternatively, or additionally, in some systems, interactions with a user may occur through a presentation layer, such as the presentation layer 1544. In these systems, the application/module ‘logic’ can be separated from the aspects of the application/module that interact with a user.

Some software architectures utilize virtual machines. In the example of FIG. 15, this is illustrated by a virtual machine 1548. A virtual machine creates a software environment where applications/modules can execute as if they were executing on a hardware machine (such as the machine 1600 of FIG. 16, for example). A virtual machine is hosted by a host operating system (e.g., operating system 1514 in FIG. 15) and typically, although not always, has a virtual machine monitor 1546, which manages the operation of the virtual machine 1548 as well as the interface with the host operating system (e.g., operating system 1514). A software architecture executes within the virtual machine 1548, such as an operating system 1550, libraries 1552, frameworks/middleware 1554, applications 1556, and/or a presentation layer 1558. These layers of software architecture executing within the virtual machine 1548 can be the same as corresponding layers previously described or may be different.

Example Machine Architecture and Machine-Readable Medium

FIG. 16 is a block diagram illustrating components of a machine 1600, according to some example embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 16 shows a diagrammatic representation of the machine 1600 in the example form of a computer system, within which instructions 1616 (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine 1600 to perform any one or more of the methodologies discussed herein may be executed. The instructions 1616 transform the general, non-programmed machine into a particular machine programmed to carry out the described and illustrated functions in the manner described. In alternative embodiments, the machine 1600 operates as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1600 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 1600 may comprise, but not be limited to, a server computer, a client computer, a PC, a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular telephone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions 1616, sequentially or otherwise, that specify actions to be taken by the machine 1600. Further, while only a single machine 1600 is illustrated, the term ‘machine’ shall also be taken to include a collection of machines 1600 that individually or jointly execute the instructions 1616 to perform any one or more of the methodologies discussed herein.

The machine 1600 may include processors 1610, memorystorage 1630, and I/O components 1650, which may be configured to communicate with each other such as via a bus 1602. In an example embodiment, the processors 1610 (e.g., a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), an ASIC, a Radio-Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 1612 and a processor 1614 that may execute the instructions 1616. The term ‘processor’ is intended to include multi-core processors that may comprise two or more independent processors (sometimes referred to as ‘cores’) that may execute instructions contemporaneously. Although FIG. 16 shows multiple processors 1610, the machine 1600 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiples cores, or any combination thereof.

The memory/storage 1630 may include a memory 1632, such as a main memory, or other memory storage, and a storage unit 1636, both accessible to the processors 1610 such as via the bus 1602. The storage unit 1636 and memory 1632 store the instructions 1616 embodying any one or more of the methodologies or functions described herein. The instructions 1616 may also reside, completely or partially, within the memory 1632, within the storage unit 1636, within at least one of the processors 1610 (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine 1600. Accordingly, the memory 1632, the storage unit 1636, and the memory of the processors 1610 are examples of machine-readable media.

As used herein, ‘machine-readable medium’ means a device able to store instructions and data temporarily or permanently and may include, but is not limited to, random-access memory (RAM), read-only memory (ROM), buffer memory, flash memory, optical media, magnetic media, cache memory, other types of storage (e.g., Erasable Programmable Read-Only Memory (EEPROM)), and/or any suitable combination thereof. The term ‘machine-readable medium’ should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) able to store the instructions 1616. The term ‘machine-readable medium’ shall also be taken to include any medium, or combination of multiple media, that is capable of storing instructions (e.g., instructions 1616) for execution by a machine (e.g., machine 1600), such that the instructions, when executed by one or more processors of the machine (e.g., processors 1610), cause the machine to perform any one or more of the methodologies described herein. Accordingly, a ‘machine-readable medium’ refers to a single storage apparatus or device, as well as ‘cloud-based’ storage systems or storage networks that include multiple storage apparatus or devices. The term ‘machine-readable medium’ excludes signals per se.

The I/O components 1650 may include a wide variety of components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific I/O components 1650 that are included in a particular machine will depend on the type of machine. For example, portable machines such as mobile phones will likely include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I/O components 1650 may include many other components that are not shown in FIG. 16. The I/O components 1650 are grouped according to functionality merely for simplifying the following discussion and the grouping is in no way limiting. In various example embodiments, the I/O components 1650 may include output components 1652 and input components 1654. The output components 1652 may include visual components (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor, resistance mechanisms), other signal generators, and so forth. The input components 1654 may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or another pointing instrument), tactile input components (e.g., a physical button, a touch screen that provides location and/or force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like.

In further example embodiments, the I/O components 1650 may include biometric components 1656, motion components 1658, environmental components 1660, or position components 1662, among a wide array of other components. For example, the biometric components 1656 may include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram based identification), and the like. The motion components 1658 may include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The environmental components 1660 may include, for example, illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors to detect concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment. The position components 1662 may include location sensor components (e.g., a Global Position System (GPS) receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies. The I/O components 1650 may include communication components 1664 operable to couple the machine 1600 to a network 1680 or devices 1670 via a coupling 1682 and a coupling 1672, respectively. For example, the communication components 1664 may include a network interface component or other suitable device to interface with the network 1680. In further examples, the communication components 1664 may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi®, components, and other communication components to provide communication via other modalities. The devices 1670 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB).

Moreover, the communication components 1664 may detect identifiers or include components operable to detect identifiers. For example, the communication components 1664 may include Radio Frequency Identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional bar codes such as Universal Product Code (UPC) bar code, multi-dimensional bar codes such as Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode. PDF417, Ultra Code, UCC RSS-2D bar code, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals). In addition, a variety of information may be derived via the communication components 1664, such as location via Internet Protocol (IP) geolocation, location via Wi-Fi® signal triangulation, location via detecting an NFC beacon signal that may indicate a particular location, and so forth.

Transmission Medium

In various example embodiments, one or more portions of the network 1680 may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a WAN, a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, another type of network, or a combination of two or more such networks. For example, the network 1680 or a portion of the network 1680 may include a wireless or cellular network and the coupling 1682 may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile communications (GSM) connection, or another type of cellular or wireless coupling. In this example, the coupling 1682 may implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, third Generation Partnership Project (3GPP) including 3G, fourth generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX). Long Term Evolution (LTE) standard, others defined by various standard-setting organizations, other long range protocols, or other data transfer technology.

The instructions 1616 may be transmitted or received over the network 1680 using a transmission medium via a network interface device (e.g., a network interface component included in the communication components 1664) and utilizing any one of a number of well-known transfer protocols (e.g., HTTP). Similarly, the instructions 1616 may be transmitted or received using a transmission medium via the coupling 1672 (e.g., a peer-to-peer coupling) to the devices 1670. The term ‘transmission medium’ shall be taken to include any intangible medium that is capable of storing, encoding, or carrying the instructions 1616 for execution by the machine 1600, and includes digital or analog communications signals or other intangible media to facilitate communication of such software.

Language

Throughout this specification, plural instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed concurrently, and nothing requires that the operations be performed in the order illustrated. Structures and functionality presented as separate components in example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of the subject matter herein.

Although an overview of the inventive subject matter has been described with reference to specific example embodiments, various modifications and changes may be made to these embodiments without departing from the broader scope of embodiments of the present disclosure. Such embodiments of the inventive subject matter may be referred to herein, individually or collectively, by the term ‘invention’ merely for convenience and without intending to voluntarily limit the scope of this application to any single disclosure or inventive concept if more than one is, in fact, disclosed.

The embodiments illustrated herein are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed. Other embodiments may be used and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. The Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

As used herein, the term ‘or’ may be construed in either an inclusive or an exclusive sense. Moreover, plural instances may be provided for resources, operations, or structures described herein as a single instance. Additionally, boundaries between various resources, operations, modules, engines, and data stores are somewhat arbitrary, and particular operations are illustrated in a context of specific illustrative configurations. Other allocations of functionality are envisioned and may fall within a scope of various embodiments of the present disclosure. In general, structures and functionality presented as separate resources in the example configurations may be implemented as a combined structure or resource. Similarly, structures and functionality presented as a single resource may be implemented as separate resources. These and other variations, modifications, additions, and improvements fall within a scope of embodiments of the present disclosure as represented by the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. 

1. A computer system, comprising: one or more processors; and a non-transitory computer readable storage medium storing instructions that when executed by the one or more processors cause the computer system to perform operations comprising: obtaining one or more sample suggested candidate member profiles in an online system having a plurality of members; obtaining one or more sample search result member profiles in the online system; identifying unique pairs of member profiles, each unique pair consisting of one of the one or more sample suggested candidate member profiles and one of the one or more sample search result member profiles; generating, for each of the unique pairs of member profiles, a label using a score generated from log information of the online system, the log information including historical records of searcher feedback regarding members of the online system, the score being higher if the searcher expressed acceptance of the sample search result member profile in a search session; and inputting the generated labels into a machine learning algorithm to train a combined ranking model, wherein the combined ranking model is configured to output ranking scores for search result member profiles.
 2. The system of claim 1, the system further comprising a time machine function configured to: receive: a member profile for a member of the online system; and standardized log information in the log information of the online system; and generate a position timeline for the member based on position-derived data in the standardized log information; generate an education timeline for the member based on education-derived data in the standardized log information; produce a member timeline for the member as specified by a given start date and given end date, the member timeline being based on the position timeline and the education timeline; and provide a snapshot of the member profile as of a certain day in the past, the snapshot being based on the member timeline.
 3. The system of claim 2, wherein the generating the label for each of the unique pairs of member profiles, is based at least in part on the member timeline.
 4. The system of claim 1, wherein the online system hosts a social networking service including the member profiles,
 5. The system of claim 4, wherein the log information further includes records of past user feedback by the searcher, the user feedback including interaction with member profiles in the social networking service.
 6. The system of claim 5, wherein: a high score is used if the searcher expressed approval of the member corresponding to the member corresponding to the sample search result member profile in a search session, a low score if no interaction occurred in the search session or the searcher expressed rejection of the member corresponding to the member corresponding to the sample search result member profile in a search session; and a medium score is used if the searcher expressed deferral of the member corresponding to the member corresponding to the sample search result member profile in a search session, the medium score corresponding to a value between the low score and the high score.
 7. The system of claim 4, wherein a search session includes a period of time between a searcher initiating a search and the searcher submitting an unrelated search or logging off the social networking service.
 8. The system of claim 1, wherein a search session is a candidate browsing session.
 9. The system of claim 1, wherein the instruction set executable on the processor further cause the computer system to perform operations comprising: aggregating label scores from multiple search sessions.
 10. The system of claim 1, wherein the instruction set executable on the processor further cause the computer system to perform operations comprising: ranking one or more search result member profiles using the combined ranking model.
 11. A computer implemented method, comprising: obtaining one or more sample suggested candidate member profiles in an online system having a plurality of members; obtaining one or more sample search result member profiles in the online system; identifying unique pairs of member profiles, each unique pair consisting of one of the one or more sample suggested candidate member profiles and one of the one or more sample search result member profiles; generating, for each of the unique pairs member profiles a label using a score generated from log information of the online system, the log information including historical records of searcher feedback regarding members of the online system, the score being higher if the searcher expressed acceptance of the sample search result member profile in a search session; and inputting the generated labels into a machine learning algorithm to train a combined ranking model used to output ranking scores for search result member profiles.
 12. The method of claim 11, wherein the log information further includes records of past user feedback by the searcher, the user feedback including interaction with member profiles in the online system.
 13. The method of claim 11, wherein a search session is a candidate browsing session.
 14. The method of claim 11, wherein the online system hosts a social networking service including the member profiles.
 15. The method of claim 14, wherein a search session includes a period of time between a searcher initiating a search and the searcher submitting an unrelated search or logging off the social networking service.
 16. The method of claim 11, further comprising aggregating label scores from multiple search sessions.
 17. The method of claim 11, further comprising ranking one or more search result member profiles using the combined ranking model.
 18. A non-transitory machine-readable storage medium comprising instructions, which when implemented by one or more machines, cause the one or more machines to perform operations comprising: obtaining one or more sample suggested candidate member profiles in a social networking service; obtaining one or more sample search result member profiles in the social networking service; identifying unique pairs of member profiles, each unique pair consisting of one of the one or more sample suggested candidate member profiles and one of the one or more sample search result member profiles; generating, for each of the unique pairs member profiles a label using a score generated from log information of the social networking service, the log information including historical records of searcher feedback regarding members of the social networking service, the score being higher if the searcher expressed acceptance of the sample search result member profile in a search session; and inputting the generated labels into a machine learning algorithm to train a combined ranking model used to output ranking scores for search result member profiles.
 19. The non-transitory machine-readable storage medium of claim 18, wherein the log information further includes records of past user feedback by the searcher, the user feedback including interaction with member profiles in the social networking service.
 20. The non-transitory machine-readable storage medium of claim 18, wherein a search session includes a period of time between a searcher initiating a search and the searcher submitting an unrelated search or logging off the social networking service. 